home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
bbs
/
nmfwd205.zip
/
NMFWD.CFG
< prev
next >
Wrap
Text File
|
1996-06-18
|
28KB
|
706 lines
;*****************************************************************************
;* *
;* (C) Copyright 1991-1996 Alberto Pasquale *
;* *
;* A L L R I G H T S R E S E R V E D *
;* *
;*****************************************************************************
;* *
;* NmFwd is NOT free-software, it is distributed under the ShareWare *
;* concept ! If you regularly use it, you should register. *
;* See REGISTER.DOC for more details on how to register your copy. *
;* *
;*****************************************************************************
;* *
;* How to contact the author: Alberto Pasquale of 2:332/504@fidonet *
;* alberto.pasquale@mo.nettuno.it *
;* Viale Verdi 106 *
;* 41100 Modena *
;* Italy *
;* *
;*****************************************************************************
;
;
; Sample NmFwd 2.05 Control file
;
;
;RegKey RegistrationKey ; If you are a registered user, put your
; ; registration key here (not case sensitive)
;
;
; S Y S T E M
;
;
; MaxPrm <filename>
;
; Points to the Maximus 3.xx PRM file.
; If the MAXIMUS environment variable is defined, this statement is an
; optional override.
;
MaxPrm c:\max\max.prm ; Maximus Prm file
;
; MultiLineDesc <nnn> [<c>]
;
; Specifies the continuation column (0 based) and character
; for multi-line descriptions in files.bbs.
;
; For example, to have the 2nd and following description lines in
; files.bbs preceded by 31 spaces, use:
;
; MultiLineDesc 31
;
; To have the continuation lines preceded by a
; '|' character, use:
;
; MultiLineDesc 29 |
;
MultiLineDesc 31
;
; The "SquishCfg" file is changed by Areafix.
; Some cfg options are searched for in SquishCfg:
; Address, BinkPoint, NetFile, NetArea, PointNet, LogFile, Outbound,
; Password, Maxpkt, KillInTransit, Track
;
; If you want to add or override some option, you can add any of the
; previous statements in this file. The overrides must be after the
; SquishCfg statement, so that they can overwrite the specifications
; previously got from the Squish cfg file.
;
; ATTENTION: the log file is opened when a logfile specification is first
; encountered. If you want to override the LogFile statement of squish.cfg
; you must specify "LogFile" before "SquishCfg" !
; The "-l<logfile>" command line swith is a global override.
;
; The new "include" statement of squish.cfg is NOT supported: you must
; use a unique Squish.Cfg file if you want NmFwd to work correctly.
;
SquishCfg c:\max\squish.cfg ; The Squish configuration file.
;
;
; If you have the "BinkPoint" verb active in SquishCfg, NmFwd must know
; which points (if any) have to be addressed using the 3D fakenet
; address.
; The "3DPoint <point> [<point>] ..." statement allows you to give NmFwd
; the necessary information.
; Multiple 3DPoint lines are allowed.
; If "BinkPoint" is not used (Squish in 3D mode) NmFwd assumed that all
; the points are 3D, so that you can comment out the 3DPoint statement.
;
3DPoint 1 2 4 5 6 ; List of fakenet Points
;
;
TmpPath c:\nmtmp ; Path for temporary files
;
;
MsgSize 16000 ; set the maximum size for messages generated
; ; by the various robots: defaults to 7000.
; ; Output will be automatically divided into
; ; multiple messages of this size.
;
FwdMsgSize 260000 ; set the size of the message forward buffer.
; ; Defaults to 32000
; ; Forwarded netmail messages will be truncated
; ; at this size, so make sure this number is large
; ; enough (as the buffer of your mail processor).
;
MarkReceived ; Mark the messages addressed to the various
; ; robots as received. Otherwise they are deleted
; ; after execution.
; ; !!! If you have problems with NmFwd and Golded,
; ; please be sure this statement is active.
;
; WrapDesc [<indent> [<right>]] ; Allows to indent the file descriptions
; reported by the filemanager.
; <indent> is the indentation for 2nd
; and consecutive lines (default 0);
; <right> is the maximum column number
; (default 79).
;
WrapDesc 31 79 ; Align file description
;
;
;
; B O S S E N A B L E
;
;
; If you are a remote SysOp and you usually operate from your point, you
; should be aware that you cannot send netmail messages with the ".0"
; address from your 4D point through your Boss, as you could with a 3D
; point. The reason is that Squish (on your Boss) automatically adds
; any missing "^AFMPT n" kludge to all messages tossed from PKTs that
; come from 4D points.
;
; So, if you need the capability to send netmail messages to Areafix,
; Raid, VoteMgr of your uplinks from your point, you need the BossEnable
; verb.
;
; When BossEnable is active, if a netmail message coming from one of
; your points has the "*BOSS*" (case insensitive) string at the beginning
; of its subject, the string and the "^AFMPT n" kludge are removed.
;
; No space is removed after the "*BOSS*" string, so don't leave any
; space between this string and the actual subject if you do not need
; spaces before the subject !
;
;
BossEnable ; Enables .0 netmail msgs from 4D points
;
;
;
; B O S S R O U T I N G
;
;
; If you are using BinkleyTerm (TradeMark of Bit Bucket Software)
; in the 5D mode (no "privatenet" in binkley.cfg) and Squish in 4D mode
; ("BinkPoint" in squish.cfg) you should have noted that you cannot
; send a crash netmail to a point through its boss, as you could in a
; fakenet environment.
;
; If you do not comment out the "BossRoute" statement, NmFwd will send
; to your Outbound.Sq and route to their boss all the crash and direct
; flavoured messages addressed to points that are not found in your V7
; nodelist or that have a NULL phone number.
;
; Thus you have the good old boss-routing feature while retaining the
; capability of directly calling a point if it has a valid phone number
; in your V7 nodelist. Please note that a point in your nodelist could
; have been redirected to its boss: in this case Binkley will call it
; through its boss phone number.
;
BossRoute ; Route Crash/Direct msgs for points to their boss
;
;
;
; B O S S F I X
;
;
; Squish 1.01 has a bug: when operating in 4D mode, the messages
; addressed to points are automatically routed to their Boss BUT Squish
; does NOT set the packet password for the Boss in the routed packet.
;
; So, if you are operating in 4D mode using packet passwords and you
; have some downlinks, you cannot use the
; "Send <flavour> <node> [<nodes>...]" command in route.cfg.
; You can safely use the "Route <flavour> <node> .All" command for each
; of your downlinks (explicitly routing points to their Boss).
;
; An easier way is to enable the "BossFix" statement